-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Clean Up Etcd Worker Actor #5323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean Up Etcd Worker Actor #5323
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5323 +/- ##
==========================================
- Coverage 81.03% 76.71% -4.32%
==========================================
Files 239 240 +1
Lines 14245 14242 -3
Branches 594 616 +22
==========================================
- Hits 11543 10926 -617
- Misses 2702 3316 +614
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bdoyle0182 Thank you for handling this.
The changes look great to me with a minor nit.
expectMsg(FinishWork(key)) | ||
} | ||
|
||
it should "retry request after failure if lease does not exist" in { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also add other negative tests for RegisterData
and RegisterInitialData
?
I merging this as-is because my comment is incidental. |
* clean up etcd worker actor * revert etcd client local change for unit testing * fix scala 2.13 compilation Co-authored-by: Brendan Doyle <[email protected]>
Description
I don't think this is the root of my issue with the scheduler not learning that a container has been removed, but nevertheless this is a valuable refactor to make sure everything is thread safe in this actor.
There should be no behavior change to the actor at all, should be 100% refactor.
This pr does a couple things:
lease
from future callbacks through 3.Related issue and scope
My changes affect the following components
Types of changes
Checklist: